From: "Stefan Stuntz"Date: Mon, 24 Jun 1996 19:23:37 +0100 X-Mailer: IntuiNews 1.3b Beta 7 (2.2.96) Subject: Registration Numbers (was Re: A problem and three classes.) Message-ID: <81322823@magic.informatik.tu-muenchen.de> Organization: Home of MUI Resent-Message-ID: <"U8AXH3.0.YR6.7ikpn"@susi> Resent-From: mui@sunsite.Informatik.RWTH-Aachen.de Reply-To: mui@sunsite.Informatik.RWTH-Aachen.de X-Mailing-List: archive/latest/1626 X-Loop: mui@sunsite.informatik.rwth-aachen.de Precedence: list Resent-Sender: mui-request@sunsite.Informatik.RWTH-Aachen.de Content-Type: text Content-Length: 1004 X-Lines: 24 Status: RO Troels Walsted Hansen wrote in article <651.6749T913T923@stud.cs.uit.no>: > >> Yes, I read that part of the docs too, but my registration number is some > >> 10 digits long, so it doesn't fit into 15 bits. > > > >Wow - MUI now has more registered users than there are people in the > >world. ;-) I guess Stefan isn't using a simple incremental numbering > >scheme. > > He must have changed it then, because my reg. number (registered October 93) > has only four digits and the first is 0. Maybe he got more than 9999 > registrations? :) Old MUI serial numbers were composed of 4 digits with the first one describing the registration site where the key came from. New serial numbers are calculated as a checksum from address data. Unfortunately, I forget that this new checksum doesnt fit into 16 bits anymore, so the tag value calculation fails. If you've got a new serial number and need tag values for public custom classes, please ask Klaus Melchior (kmel@eifel.tng.oche.de). -- Greetings, Stefan From: "Stefan Stuntz" Date: Sun, 30 Jun 1996 14:20:23 +0100 X-Mailer: IntuiNews 1.3b Beta 7 (2.2.96) Subject: Re: Registration Numbers (was Re: A problem and three classes.) Message-Id: <81323172@magic.informatik.tu-muenchen.de> Organization: Home of MUI Resent-Message-ID: <"LLAXX.0.Ed3.Y6drn"@susi> Resent-From: mui@sunsite.Informatik.RWTH-Aachen.de Reply-To: mui@sunsite.Informatik.RWTH-Aachen.de X-Mailing-List: archive/latest/1694 X-Loop: mui@sunsite.informatik.rwth-aachen.de Precedence: list Resent-Sender: mui-request@sunsite.Informatik.RWTH-Aachen.de Content-Type: text Content-Length: 1157 X-Lines: 28 Status: RO Flavio Stanchina wrote in article <199606291222.OAA60886@venere.inet.it>: > >> If you've got a new serial number and need tag values for public custom > >> classes, please ask Klaus Melchior (kmel@eifel.tng.oche.de). > MO> And for non public classes? > > I'm joining the question. Think about this: I have my private class with > all its tag values, and I use that nice public class whose tag values I > cannot control. How can I be sure that my tags don't conflict? If everybody uses the <<16 scheme with his (old) serial number in public and private custom classes, there wont be any conflicts. Tag values that start with oldsernumber<<16 are always reserved for the owner of this serial number. Only people without an old serial number need to apply for a reserved value which will be chosen in a way that it doesnt conflict with other old serial numbers. In any case, authors of public custom classes must register the name of their class before release. Furthermore, please ask here before starting to work on something. Altough there are only very few custom classes at the moment, we are already starting to get dupes. -- Greetings, Stefan